Human-readable metadata scan - #6519
Conversation
| executionHintsOpt = new Option(null, "execution-hints", true, "Execution hints map"); | ||
| scanServerOpt = | ||
| new Option("cl", "consistency-level", true, "set consistency level (experimental)"); | ||
| decodeMetadataOpt = new Option("dm", "decode-metadata", false, |
There was a problem hiding this comment.
I'm not sure that we need an option. If the user has the ability to scan the metadata, then we should just show them the un-obfuscated metadata entry.
There was a problem hiding this comment.
Doesn't accumulo already have formatters? metadataformatter that extends default formatter could be a better option and obviate the need for an option. also could be default?
There was a problem hiding this comment.
It's a good idea, but I think the intention is to remove formatters. See #3265.
There was a problem hiding this comment.
Yes, thank you. I encountered this last year sometime when testing 4.0, but I have a very poor memory....
Should this option be flipped? On by default, old method an option just in case someone relies on the encoded form?
I think it's pretty fair to say 4.0 changes the output, though.
There was a problem hiding this comment.
My goal was to avoid changing the normal metadata scan output in a way that might make users think that the decoded form is the actual stored metadata representation. I figured adding a new option, allows for the default behavior to remain unchanged, and users only get the decoded/human-readable form when they explicitly ask for it
3 participants
Closes issue #3772
StoredTabletFile.toStringto usetoMinimalString()making tablet file ranges readable in logs and other outputs.ScanCommandto decode file and scan column qualifiers when scanning metadata tablesFileMetadataUtilloggin to use SLF4J placeholders